Secure manufacturing of programmable devices

ABSTRACT

According to an embodiment, a programmable logic device includes a plurality of logic blocks and a logic unit. The logic blocks are grouped into one or more partitions. The logic unit controls external access to the one or more partitions, controls programming of the one or more partitions and controls interconnection and operation of the one or more partitions during operation of the programmable logic device.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No. 61/101,441 filed on Sep. 30, 2008, which is incorporated herein by reference in its entirety.

BACKGROUND

Programmable devices such as FPGAs (field programmable gate arrays) are devices that can be designed and programmed via programming tools to operate in a wide variety of applications. Programmable devices include logic elements and interconnect resources that can be configured as necessary to operate in a particular application. The logic elements and interconnect resources are configured in collections known as logic blocks, which often times perform a specific function. Programmable devices also typically include other resources such as Random Access Memory (RAM) and other predefined blocks of logic such as a Digital Signal Processor (DSP), a Central Processing Unit (CPU), adders, multipliers, etc. During operation of the programmable device, the logic blocks and other resources are often shared by multiple logic elements.

Designs are typically partitioned into separate functional modules that include many logic blocks. Some of the functional modules may be purchased or licensed from a vendor for integration with other functional modules into the programmable device. These intellectual property modules often have certain rights and restrictions. In addition, many applications require a certain degree of system security and integrity. Functional modules employed in these types of applications have stricter security and integration requirements than those that are not since weaknesses and vulnerabilities can compromise the security and integrity of the system that they serve.

Many applications require secure programming and operation of programmable logic devices. For example, in certain applications, it is necessary to reprogram or upgrade a functional module regardless of whether the programmable device is operating or not. During operation of the programmable device, it may also be necessary to enable and/or disable different functional modules without affecting other functional modules. Also, suppliers of functional modules need to protect their intellectual property when integrated with other functional modules in a third-party design. There may be a need to identify and be compensated for each instance or use of a vendor's intellectual property. These and other security and system integrity functions present various challenges during different phases of programmable device development and use. Security breaches can occur during the design, programming and operation of a programmable device absent sufficient mechanisms for protecting the functional modules included in the device.

SUMMARY

According to an embodiment, a programmable logic device includes a plurality of logic blocks and a logic unit. The logic blocks are grouped into one or more partitions. The logic unit controls external access to the one or more partitions, controls programming of the one or more partitions and controls interconnection and operation of the one or more partitions during operation of the programmable logic device.

Those skilled in the art will recognize additional features and advantages upon reading the following detailed description, and upon viewing the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an embodiment of a secure programmable logic device.

FIG. 2 illustrates a secure programmable logic device during different phases of design, programming and operation.

FIG. 3 illustrates an embodiment of a logic unit and communication control elements associated with a secure programmable logic device.

FIG. 4 illustrates an embodiment of a logic unit, communication control elements and monitoring elements associated with a secure programmable logic device.

FIG. 5 illustrates an embodiment of communication control elements coupled to partitioned logic blocks of a secure programmable logic device.

FIG. 6 illustrates an embodiment of a partition information table accessed by a logic unit of a secure programmable logic device.

DETAILED DESCRIPTION

Secure programmable logic devices and methods of designing, programming and operating the same are disclosed herein. The integrity and security of functional modules embodied within a programmable logic device such as an FGPA are securely maintained throughout the design, programming and operation of the device. To provide and maintain the security and integrity of the functional modules, programmable device and system as a whole, logic blocks associated with the different functional modules are grouped into one or more partitions. Each partition includes a plurality of logic blocks which can be programmed to perform different functions. The programmable device authenticates access rights before permitting programming access to the different partitions. In addition, the programmable device controls partition programming so that various partition requirements are satisfied. This way, the security and integrity of the programmable device is not compromised during partition programming. The programmable device also controls and monitors the interconnection and communication between the partitions so that the partition requirements are also satisfied during operation and re-programming of the device. Accordingly, system security is automatically maintained throughout the design, programming and operation of the programmable device.

The programmable device can also automatically maintain security between partition interconnections to protect proprietary data. This way, some partitions can be prevented from connecting to, observing, driving or otherwise interfacing with other partitions when secure data is involved. In addition, the programmable device can isolate, protect and control access to shared resources such as RAM, DSPs, CPUs, adders, multipliers, etc. The programmable device also automatically manages the isolation and re-programming of partitions during normal device operation as well as enabling and disabling different ones of the partitions during normal operation all while maintaining system security and integrity. Furthermore, the programmable device can track the use of different IP (intellectual property) modules for which a per-use license or other fee arrangement may be owed.

FIG. 1 illustrates an embodiment of a secure programmable logic device 100. The device 100 includes one or more different partitions 102, 104 of logic blocks 106. FIG. 1 shows two partitions 102, 104, but the device 100 may include any suitable number of partitions. The logic blocks 106 are coupled to communication control elements (CCEs) 108 for interfacing to other logic blocks 106 via switch elements 110. Interconnections 112 between the switch elements 110 can be single-wire or bus-based connections or some combination of both. In each case, programming access to the partitions 102, 104 as well as actual partition programming are controlled by a logic unit 114 included in or associated with the programmable device 100. The logic unit 114 can be included in the programmable device 100 or external to the device 100. The logic unit is referred to herein in abbreviated form as FMU (fabric management unit). The FMU 114 also controls the interconnection and operation of the partitions 102, 104 during operation of the programmable logic device 100. Accordingly, system security and integrity is maintained during the design, programming and operation of the programmable device 100.

The FMU 114 controls programming access to the partitions 102, 104 based on authentication information 116 stored by a memory component 118 included in or associated with the programmable device 100 such as ROM (read-only memory), flash memory, register or other type of volatile or non-volatile memory component. In other embodiments, the authentication information 116 is requested from or provided by a source external to the programmable device 100. In one embodiment, the authentication information 116 includes a secure key associated with each entity permitted to program one or more of the partitions 102, 104. Programming access to a secure partition is granted when possession of a proper key for that partition is verified by the FMU 114, e.g., by looking the key up in the memory 118 and performing any authentication mechanism involving the stored key associated with the secure partition. The authentication process can be skipped when an entity seeks programming access to an un-secure partition.

After successful authentication, the corresponding secure partition can be programmed. In one embodiment, programming data is provided to the programmable device 100 in encrypted form. According to this embodiment, the authentication information 116 stored in the memory 118 includes one or more encryption keys for decrypting the programming data. In either case, the partition 102, 104 for which access is granted is then programmed. The memory 118 also stores partition information 120 used by the FMU 114 to control how the partitions 102, 104 can be programmed, including bounds checking as will be described in more detail later. The FMU 114 also uses the partition information 120 to control the interconnection and operation of the partitions 102, 104 during programming and operation of the programmable device 100 to maintain security and integrity between the partitions 102, 104 during programming and operation. For example, the first partition 102 can be operating while the second partition 104 is being reprogrammed. In this case, the FMU 114 controls the interconnect 112 between the partitions 102, 104 so that the first partition 102 is isolated.

FIG. 2 illustrates an embodiment of a methodology for designing secure partitions 102, 104, preparing the programmable device 100 to accept the secure partitions 102, 104, creating the partition information 120 and programming the device 100. The partitions 102, 104 can be formed in a secure design environment 200 from one or more contiguous collections of logic blocks 106. Two or more interconnected partitions 102, 104 can be arranged adjacent to one another or physically separated. The secure design is then overlaid on the programmable device 100 to generate a secure design overlay 202. The FMU 114 is then programmed 204 at a secure factory location 206. In one embodiment, the programmable device 100 is also provided with a master authentication key. The master authentication key is used at a manufacturing or customer location 208 to control which entity or entities are permitted to program the partition information 120 into the FMU 114. After the master key is authenticated 210, partition information programming is permitted 212. Authentication keys for enabling further partition programming can also be provided now or earlier in the process. At this point in the process, the programmable device 100 has been securely partitioned and programmed with information that controls programming (and re-programming) access to the partitions 102, 104 and how the different partitions 102, 104 can be programmed (and re-programmed). In one embodiment, the partition information 120 is stored in a partition information table 214 included in or associated with the programmable device 100. The authentication and partition information 116, 120 are subsequently used at a programming location 216 to program the device 100 with one or more partition designs 218. The FMU 114 uses the authentication information 116 to determine whether the programming device is permitted to access any of the partitions 102, 104. If so, partition programming commences and is controlled by the FMU 114 based on the partition information 120 stored in the partition information table 214. The authentication and partition information 116, 120 is also used by the FMU 114 to control the interconnection and operation of the partitions 102, 104 during operation of the programmable logic device 100 and reprogramming and reconfiguration of the device 100.

In one embodiment, the FMU 114 is a collection of circuits implemented in one of many ways to perform various authentication and security functions. The authentication and partition information 116, 120 used by the FMU 114 to maintain system security and integrity can be locally stored by the FMU 114 or by a different memory component of the programmable device 100. In either case, the FMU 114 stores, protects and uses master and/or other key information for performing authentication and programming data decryption. The FMU 114 can interact with external programming devices to verify programming rights for partition data using the key information. The FMU 114 can also authenticate external programming devices and permit the devices to provide or update the partition information 120 or portions of the partition information 120 after being verified. This way, the partition information 120 is safely and securely downloaded, stored, protected and retrieved under control of the FMU 114.

The FMU 114 uses the partition information 120 during device programming and operation. Accordingly, some portions of the partition information 120 may pertain to device programming (and re-programming) while other portions of the partition information 120 may pertain to actual device operation. During partition programming, the FMU 114 enforces the programming rules specified by the partition information 120. For example, the FMU 114 can enforce access rights to allow or prevent programming of particular partitions 102, 104. The FMU 114 can also validate partition programming data and prevent programming or re-programming responsive to errors or violations. In one embodiment, this includes bounds checking to ensure that programming data associated with one of the partitions 102, 104 to be programmed is confined to the area of the programmable device 100 allocated to that partition and prevents the programming data from flowing through to other partitions 102, 104. The FMU 114 can also protects the interconnect privacy between partitions 102, 104 during the programming process. In one embodiment, the partition information 120 includes an “Interconnect Configuration Mask” which identifies specific common resources in the programmable device 100 which are reserved for specific ones of the partitions 102 104. The FMU 114 uses the Interconnect Configuration Mask to ensure that configuration streams for other partitions 102, 104 do not violate the reservations indicated by the Mask. The partition information 120 may also indicate which partitions 102, 104 can be fully or partially reconfigured and which ones cannot. The FMU 114 uses the reconfiguration information to prevent reprogramming of protected partitions or protected partition functions. The reconfiguration information can also indicate the number of reconfiguration attempts which are permitted. The FMU 114 prevents additional reconfiguration attempts once the limit is reached.

During operation of the programmable device 100, the FMU 114 enforces the operating rules specified by the partition information 120. The FMU 114 can isolate partitions 102, 104 from one another based on certain ones of the programming rules. The FMU 114 can also isolate partitions 102, 104 from programmable device 1/0 (input/output) and or from shared resources of the programmable device 100 such as memory, DSP, CPU, etc. The FMU 114 also uses the operating rules to resolve shared resource access rights and criteria. Accordingly, the FMU 114 is aware of the structure of the programmable device 100 and can be implemented in a centralized or distributed manner. The FMU 114 can be partly or fully located within the programmable device 100 or located externally to the device 100 and can be implemented in hardware or a suitable combination of hardware with mil software or firmware.

FIG. 3 illustrates an embodiment of the FMU 114. According to this embodiment, the FMU 114 includes a controller 300, a master key table 302 and the partition information table 214. The controller 300 performs authentication based on the information stored in the master key table 302 and enforces the rules indicated by the information stored in the partition information table 214. Information stored in the partition information table 214 is collected during the design phase and formatted appropriately for loading into the partition information table 214. In one embodiment, the FMU 114 permits a programming device having an authenticated key to download partition information 120 into the partition information table 214. The partition information table 214 includes information about the programmable logic device 100 and information specific to each partition 102, 104 which allows the FMU 114 to implement various security and control functions, e.g., as described above.

The master key table 302 includes information used by the FMU 114 to protect the partition information table 214 from unauthorized programming or re-programming. The FMU 114 uses one or more master keys stored in the master key table 302 to authenticate programming devices attempting to upload information to the partition information table 214. The master key(s) can be implemented according to any symmetric or asymmetric crypto algorithm rules.

The FMU controller 300 interfaces with the different CCEs 108. The CCEs 108 are coupled between the logic blocks 106 and the interconnection switch elements 110 of the programmable device 100. The switch elements 110 can be any suitable devices for connecting the logic blocks 106 such as switches, etc. The CCEs 108 isolate the communication paths between the logic blocks 106. The CCEs 108 are controlled by the FMU 114 and/or fabric monitoring elements (FMEs) included in the programmable device 100.

FIG. 4 illustrates an embodiment of the interconnections between the FMU 114, CCEs 108 and FMEs 400. The CCEs 108 provide an interface between the logic blocks 106 and the network interconnect features 112 included in the programmable device 100. The interconnect networks 112 can be single-wire or bus-based. In one embodiment, each CCE 108 connects to a respective logic block 106 at one interface and to a switching device 110 embedded in the interconnect network 112 at another interface. Accordingly, the CCEs 108 control communication flow between the logic blocks 106 and interconnect networks 112. The CCEs 108 can be a single-transistor switch or more complex logic structures. The CCEs 108 can be controlled by the FMU 114 and/or the FMEs 400. Either way, the CCEs 108 at least partly implement the partition rules provided to the programmable device 100 by configuring the interconnections between the logic blocks 106 and the interconnect networks 112 based on the partition information 120. The FMEs 400 are distributed throughout the programmable device 100 and monitor various operational aspects of the programmable device 100.

In one embodiment, the FMEs 400 assist the FMU 114 in monitoring operational integrity of the programmable device 100. The FMEs 400 can be coupled to the interconnect networks 112, CCEs 108 and/or the logic blocks 106 and can be implemented at the logic block level and/or the partition level depending on the type of operations being monitored. In one embodiment, one or more of the FMEs 400 report to the FMU 114 whether a partition 102, 104 attempts to access an interconnect network 112 or another partition to which the partition is not permitted access as indicated by the partition information 120 stored in the partition information table 214. In another embodiment, one or more of the FMEs 400 monitor physical operating conditions of the programmable device 100 such as temperature, voltage, current, power, etc. The FMEs 400 can also monitor partition programming activity to ensure no unauthorized re-programming or tampering occurs during operation of the programmable device 100. The FMEs 400 report to the FMU 114 when a condition is detected. The FMEs 400 can be programmed by the FMU 114, e.g., based on the partition information 120 uploaded to the programmable device 100. Alternatively, the FMEs 400 can be programmed by an external entity.

FIG. 5 illustrates an embodiment of the interconnections formed between the logic blocks 106, CCEs 108 and the interconnect networks 112. The switch devices 110 interface the CCEs 108 to the interconnect networks 112. The switches 110 steer data over the interconnect networks 112 to the appropriate CCEs 108. The CCEs 108 move data back and forth between the interconnect networks 112 and the logic blocks 106. The logic blocks 106 can be programmed based on the authentication and partition information 116, 120 to perform basic logic functions such as AND, OR, XOR etc. and/or more complex combinational functions such as decoders, mathematical functions, etc. The logic blocks 106 may include memory elements, which can be flip-flops or more complete blocks of memory such as volatile or non-volatile memory components. The logic blocks 106 can be sub-divided into smaller logic sub-blocks 500 of logic cells 502. According to this embodiment, the CCEs 108 provide interconnection points between the sub-logic blocks 500 of each logic blocks 106 and between the logic blocks 106 and the switch devices 110. The FMU 114 configures the CCEs based on the partition information 120 so that desired interconnection paths are formed and undesirable interconnection paths are prevented.

FIG. 6 illustrates an embodiment of the partition information table 214 that stores the partition information used by the FMU 114 and CCEs 108. The designer can specify partition intent during the design process. In one embodiment, the designer's intent is captured in the partition information table 214 after the partitions 102, 104 have been placed and routed. The table 214 includes several entries for use by the FMU 114 during partition programming and operation of the programmable device 100. The first entry 600 determines the bounds placed on the logic blocks 106 during programming. The FMU 114 uses partition bound information to restrict programming to the logic blocks 106 allocated for a particular partition. The FMU 114 uses the second entry 602 of the table 214 to identify the entities that have access to the partitions 102, 104. In one embodiment, the second entry 602 stores keys for identifying the entities which have access to particular ones of the partitions 102, 104. If an unauthenticated entity attempts to access a secure partition, programming access is denied by the FMU 114. These keys can also be used to prevent unauthorized reading of the partition data.

A third entry 604 in the table 214 includes security netlist overlay data. The security netlist overlay data is used by the FMU 114 during run time and determines how the different partitions 102, 104 should be interconnected. In one embodiment, the security netlist overlay data determines how the partitions 102, 104 should be connected to the interconnect networks 112. For example, certain ones of the partitions 102, 104 may be prevented from accessing other partitions or shared resources. Other ones of the partitions 102, 104 may be prevented from accessing I/O pins (not shown) of the programmable device 100. The security netlist overlay data controls these types and other types of partition interconnections. In one embodiment, the security netlist overlay data determines which CCEs 108 and/or FMEs 400 are enabled and disabled. The FMU 114 configures the CCEs 108 and/or the FMEs 400 based on the security netlist overlay data according to this embodiment. As such, the FMU 114 can maintain restricted and secure partition connections during operation of the programmable device 100.

A fourth entry 606 in the partition information table 214 identifies conditional access criteria which can be used in conjunction with the security netlist overlay data to configure partition connections and restrictions. The FMU 114 can use the conditional access criteria to control and restrict partition-to-partition communication by enabling and disabling the appropriate CCEs 108. The FMU 114 can also use the conditional access criteria to enable and disable different ones of the FMEs 400 for monitoring purposes. The conditional access criteria can also be used to control and restrict partition-to-I/O communication. For example, which partitions are permitted access to I/Os of the programmable device 100, which I/Os are monitored for activity, which FMEs 400 are best suited to monitor I/O activity, etc. can be determined based on the conditional access criteria stored in the fourth entry 606 of the partition information table 214.

A fifth entry 608 in the table 214 identifies shared resource access criteria which can be used to determine how the different partitions 102, 104 access shared resources. The shared resource access criteria determines which partitions 102, 104 are permitted to communicate with shared resources (e.g., such as RAM, EEPROM/PROM/Flash memory, DSP blocks, etc.) located outside the partitions 102, 104 and which partitions 102, 104 are not permitted to communicate with shared resources. The shared resource access criteria can be used during partition programming and/or operation of the programmable device 100. The FMU 114 can control and restrict shared resource access. Alternatively, shared resource access control can be distributed amongst the FMU 114, CCEs 108 and/or the FMEs 400 based on the information stored in the fifth entry 608 of the partition information table 214.

A sixth entry 610 in the table 214 includes an interconnect access control mask. The interconnect access control mask enables the FMU 114 to prevent certain partitions 102, 104 from observing and/or driving communication resources associated with other partitions. The FMU 114 can perform communication resource management based on the interconnect access control mask at a global, regional, or local level within the programmable device fabric 100. Accordingly, the FMU 114 can control when the partitions 102, 104 gain access to certain network interconnect resources 110, 112 much the same way a memory management unit controls the use of bus resources in a memory system. The FMU 114 can perform arbitration between the different partitions 102, 104 so that the communication preferences indicated by the interconnect access control mask are implemented by the programmable device 100. The partition information table 214 can be organized as a single table for all partitions 102, 104 or a separate table for each partition or group of the partitions 102, 104.

Described next are various details relating to the design, programming and operation of the programmable logic device 100. During the design phase, a designer is permitted to specify and capture a particular partition intent. For example, the designer can isolate or connect partitions 102, 104 using certain criteria. The partition information 120 is downloaded to the programmable device 100, e.g., into the partition information table 214. Authentication information 116 can also be downloaded to the programmable device 100 at this point to indicate which entities should be granted programming access to the partitions 102, 104. Decryption information may also be downloaded to the programmable device 100 for enabling the FMU 114 to process encrypted programming data. The FMU 114 uses the authentication and partition information 116, 120 (and optional decryption information) during subsequent programming and operating phases to ensure that the designer's partition criteria are enforced, maintaining security and integrity within the system.

During the programming stage, the device 100 is programmed with the assistance of the FMU 114. The FMU 114 uses the authentication and partition information 116, 120 to perform various checks during programming. In one embodiment, programming data provided to the programmable device 100 is encrypted. According to this embodiment, the FMU 114 decrypts the programming data based on the decryption data stored by the programmable device 100. In other embodiments, the programming data may not be encrypted or only programming data associated with certain ones of the partitions 102, 104 may be encrypted. In each case, the FMU 114 enforces access rights to enable or disable partition programming based on the authentication information 116. The FMU 114 also performs bounds checking to ensure that programming data associated with one partition only affects the targeted partition and not other regions of the programmable device 100. Bounds checking may involve verifying and monitoring various boundary conditions such as interconnections between the partitions 102, 104, overlap between the partitions 102, 104, partition size, etc. The FMU 114 checks the interconnect configuration mask portion of the partition information 120 to identify specific common resources in the programmable device 100 which are reserved for a particular partition. The FMU 114 prevents programming data associated with other partitions from violating this reservation. The FMU 114 can also lock down certain ones of the partitions 102, 104 when the partition information 120 indicates that these partitions are not permitted to be subsequently reconfigured or can only be reconfigured a particular number of times.

During operation of the programmable device 100, the FMU 114, partition information table 214, CCEs 108 and/or FMEs 400 are used to implement static/pseudo-static control and monitoring of partition operation. Partition-to-partition and partition-to-I/O communications can be controlled and monitored. Access to shared resources can also be controlled and monitored. The FMU 114, partition information table 214, CCEs 108 and/or FMEs 400 also control and monitor fabric and partition integrity. This way, the designer's original partition intent is enforced throughout the design, programming and operation of the programmable device 100.

The FMU 114, partition information table 214, CCEs 108 and/or FMEs 400 are also used to control and monitor reprogramming/reconfiguring of the programmable device 100. The programmable device 100 can be partially or fully reconfigured during operation. In one embodiment, one or more of the partitions 102, 104 can be individually re-configured while the remainder of the programmable device 100 remains operational. According to this embodiment, the partitions 102, 104 that continue to operate while another partition is being reconfigured are designed to continue functional operation during the reprogramming. After authentication, the FMU 114 controls the CCEs 108 associated with the partition being reprogrammed so that the partition is isolated from the remainder of the programmable device 100. This prevents data corruption and exposure of secure data. After the programming is successfully completed, the FMU 114 re-enables the CCEs 108 according to the partition information 120, e.g., in accordance with the security netlist overlay data, the conditional access criteria, the shared resource access criteria, and/or the interconnect access mask. Upon re-enablement, the reprogrammed partition resumes normal functional operation. Accordingly, different ones of the partitions 102, 104 can be reprogrammed to improve or expand functionality of the programmable device 100 or to correct errors all while the FMU 114 maintains the designer's original partition intent.

As explained previously, the FMU 114 can be centralized or distributed. The FMU 114 can be programmed and primed in different stages. In one embodiment, the FMU base firmware is programmed in a secure factory setting. The FMU base firmware can include a state machine (which can be customer-specific), protocols and a unique FMU structure. The FMU base firmware can also include a master key for permitting general access to the FMU 114 and optional partition programming keys for authenticating programming access to different ones of the partitions 102, 104, both as previously described herein. Hardware and/or software can be provided as part of the FMU base firmware. The firmware may also identify customer-specific levels of security. At the customer site, the partition information 120 is securely uploaded to the programmable device 100, e.g., into memory 118, the partition information table 214 or both. The entity attempting to upload the partition information 120 is authenticated against the master key before the FMU 114 permits uploading of the partition information 120. This way, only verified entities are allowed to provide the partition information 120 via a secure communication with the FMU 113. In addition, the secure communication path with the FMU 114 enables the programmer to secure and protect the FMU 114 itself, e.g., by implementing the FMU 114 in secure flash or non-volatile memory or by programming a secure microcontroller component of the programmable device 100 to carry out the FMU operations. Once the FMU 114 is authenticated, the programmable device 100 is now ready to undergo full or partial bit stream programming. This can include updating the partition information table 214 and/or loading the partition programming key(s) into the FMU 114 or the partition information table 214.

Accordingly, when the programmable device 100 is programmed in a less secure environment, the secure FMU 114 can perform rights checking by validating the per-partition access keys stored in memory 116 or the partition information table 214. The FMU 114 uses the key information to validate that programming or re-programming is allowed for the corresponding partition 102, 104. The FMU 114 also performs bounds checking and interconnect configuration mask checking on incoming programming bit streams as described above. The FMU can include a counter to track the number of licenses used and control the IP subscription model.

After the programmable device 100 is successfully programmed, the partitions 102, 104 can be enabled for regular operation. The CCEs 108 isolate the different partitions 102, 104. The FMU 114 controls the CCEs 108 during operation based on the partition information 120 to enforce the designer's partition intent. In one embodiment, the interconnect networks 112 can be enabled after the partitions 102, 104 are successfully programmed. The interconnect networks 112 coupled to a particular partition 102, 104 can be disabled when that partition enters a standby mode or is ready for re-configuration. The FMU 114 can control the CCEs 108 so that access to one or more resources (e.g., blocks of memory) is enabled or blocked during run time.

The FMU 114 supports one or more operation mode keys, symmetric encryption algorithms and some interface to communicate with the partitions 102, 104. The partitions 102, 104 implement a secure protocol to communicate over this interface. For example, one or more of the interconnect networks 112 can implement a secure protocol. The designer provides an authentication and/or encryption key used by the FMU 114 to authenticate partition requests over the secure interface. The FMU 114 configures the appropriate CCEs 108 responsive to the requests. This way, the partitions 102, 104 can gain access to a bus or shared resource via the configured CCEs 108.

With the above range of variations and applications in mind, it should be understood that the present invention is not limited by the foregoing description, nor is it limited by the accompanying drawings. Instead, the present invention is limited only by the following claims and their legal equivalents. 

What is claimed is:
 1. A method of manufacturing a programmable logic device having a plurality of logic blocks, comprising: grouping the logic blocks into two or more partitions; and inserting specific operating instructions into a logic unit of the programmable logic device to control external access to the two or more partitions, control programming of the two or more partitions and control operation of and interconnection between the two or more partitions during operation of the programmable logic device; wherein inserting specific operating instructions into the logic unit to control operation of and interconnection between the two or more partitions during operation of the programmable logic device comprises inserting specific operating instructions into the logic unit to control how the two or more partitions access a shared resource of the programmable logic device.
 2. The method of claim 1, comprising: storing authentication information in the programmable logic device for use by the logic unit to control external access to the two or more partitions; and storing partition information in the programmable logic device for use by the logic unit to control programming of the two or more partitions and control operation of and interconnection between the two or more partitions during operation of the programmable logic device.
 3. The method of claim 2, further comprising authenticating access to the programmable logic device based on the authentication information before permitting storage of the partition information.
 4. The method of claim 2, comprising storing the partition information in a table accessible by the logic unit.
 5. The method of claim 1, wherein inserting specific operating instructions into the logic unit comprises programming firmware associated with the logic unit.
 6. The method of claim 5, further comprising authenticating an entity attempting to access the logic unit based on a master authentication key included with the firmware.
 7. The method of claim 5, further comprising authenticating an entity attempting to upload partition information to the programmable logic device based on one or more partition authentication keys included with the firmware.
 8. The method of claim 1, wherein inserting specific operating instructions into the logic unit comprises inserting specific operating instructions for a secure microcontroller component included in the programmable logic device.
 9. The method of claim 1, wherein inserting specific operating instructions into the logic unit comprises inserting the specific operating instructions into a secure non-volatile memory included in the programmable logic device.
 10. A programmable logic device, comprising: a plurality of logic blocks grouped into two or more partitions; and a fabric management controller circuit configured to control external access to the two or more partitions, control programming of the two or more partitions and control operation of and interconnection between the two or more partitions during operation of the programmable logic device; wherein the fabric management controller circuit is configured to control how the two or more partitions access a shared resource of the programmable logic device.
 11. The programmable logic device of claim 10, further comprising: memory configured to store authentication information for use by the fabric management controller circuit to control external access to the two or more partitions and partition information for use by the fabric management controller circuit to control programming of the two or more partitions and control operation of and interconnection between the two or more partitions during operation of the programmable logic device.
 12. The programmable logic device of claim 11, wherein the fabric management controller circuit is configured to authenticate access to the programmable logic device based on the authentication information before permitting storage of the partition information.
 13. The programmable logic device of claim 11, wherein the memory comprises a table accessible by the fabric management controller circuit.
 14. The programmable logic device of claim 10, wherein the fabric management controller circuit includes firmware.
 15. The programmable logic device of claim 14, wherein the fabric management controller circuit is configured to authenticate an entity attempting to access the fabric management controller circuit based on a master authentication key included with the firmware.
 16. The programmable logic device of claim 14, wherein the fabric management controller circuit is configured to authenticate an entity attempting to upload partition information to the programmable logic device based on one or more partition authentication keys included with the firmware.
 17. The programmable logic device of claim 10, wherein the fabric management controller circuit comprises a secure microcontroller.
 18. The programmable logic device of claim 10, wherein the fabric management controller circuit comprises secure non-volatile memory.
 19. A programmable logic device, comprising: a plurality of logic blocks grouped into two or more partitions; and means for controlling external access to the two or more partitions, controlling programming of the two or more partitions and controlling operation of and interconnection between the two or more partitions during operation of the programmable logic device; means for and inserting specific operating instructions into a logic unit of the programmable logic device to control external access to the two or more partitions, means for inserting specific operating instructions into the logic unit to control operation of and interconnection between the two or more partitions during operation of the programmable logic device comprises inserting specific operating instructions into the logic unit to control how the two or more partitions access a shared resource of the programmable logic device. 